home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
CD ROM Paradise Collection 4
/
CD ROM Paradise Collection 4 1995 Nov.iso
/
win
/
winyrn71.zip
/
TESTERS.TXT
< prev
next >
Wrap
Text File
|
1994-12-14
|
3KB
|
59 lines
**** Notes to WinYarn testers ****
Thank you for helping me to test WinYarn. I like the Yarn
program very much. I also like the Windows operating
environment (actually I like the application programs and
the better functionality and flexibility over their DOS
counterparts, but that's another argument).
WinYarn was born out of personal need. Hence, it reflects
a lot of my personal tastes. I'd like to make the program
more robust so that others might benefit. I am not, however,
out to make the program serve everyone. I've found that too
much flexibility in a program actually detracts from its
usefulness. So if you make a suggestion and it doesn't get
implemented right away, or at all, don't take it personally.
WinYarn's main design goal is to cut down on the need to shell
to DOS to run the Yarn functions and to reduce the need to
specify command line switches. I had set up PIFs to handle many
Yarn chores but had a gazillion icons setup devoted to Yarn.
Also keep in mind that WinYarn is a shell program. It is
fronting a DOS program. That means there are limitations to
what WinYarn can and can't do. There are some capabilities
that I'd like to implement but would be a chore to program
right now.
My development system is a Gateway 2000 Handbook 486SX-25
laptop. I therefore see everything in black-and-white and
at standard VGA resolutions (640x480). The screen ratio is
also squashed so items which look okay when created look
different on a regular monitor. I don't have a regular
mouse (have one of those "trackpoint" devices) so I tend
to use keyboard accelerators a lot. This is reflected in
WinYarn.
My desktop system is a clone 486SX/33. It is also limited
to standard 640x480 VGA resolution. I'm curious to know how
WinYarn looks and performs at SuperVGA resolutions.
I tend to work in a groove and may not really notice that
something is amiss, especially for options that I don't use.
For instance, I import my mail and news in separate packets.
I understand that this is not usual practice so I have added an
option (with different dialogs, buttons, etc.) to import a combined
mail/news packet. If something is broken in this path, I'll never
see it since I don't use it. Don't assume that if the capability
is there, that I use it.
If you have a bug report, please identify the type of hardware
and software configuration that you are using. This may help
me evaluate if machine differences are causing a problem.
Stan Wong
MicroMime
s.wong@ieee.org
12/16/94